{{indexmenu_n>14}}

====== PI Manager for Users ======

  - Old plugins install with their own installer somewhere.
  - Old plugins find that somewhere as before.
  - OpenCPN loads the old plugins like before
  - Old plugins are uninstalled just as before.
  - PI Installer can install new plugins and puts them elsewhere
  - PI Installer's new plugins use GetPluginDataDir and must not care where elsewhere is.
  - PI Installer's use tarballs and metadata.xml for installation.

PI Installer after selection of "+" \\ {{:opencpn:dev:pi-installer-screen-1.png?400|After hit +}}

PI Installer downloading after selection of "Upload" or "Reinstall" \\ {{:opencpn:dev:pi-installer-screen-2-download.png?400|Downloading}}

PI Installer download completed and plugin installed \\ {{:opencpn:dev:pi-installer-screen-3-installed.png?400|Installed}}

PI Installer incompatible notice \\ {{:opencpn:dev:pi-installer-plugin-incompatible-notice.png?400|Incomplatible}}

PI Installer selection of Catalogs \\ {{:opencpn:dev:pi-installer-screen-5.png?400|Catalog Selection}}

====   ====

==== New installation destination path ====

Operation of plugins may have to be changed for User "ease out of the box" because right now EG: for Windows)

Plugin Packages (now)

  * Installation Directory: C:/ProgramFiles (x86)/OpenCPN [version for parallel installations]/plugins/
  * User writable Data directory: %ProgramData%/OpenCPN/plugins/…

Plugin Manager (future)

  * Installation Directory: %LOCALAPPDATADIR%/OpenCPN/plugins/ (different)
  * User writable Data directory: %ProgramData%/OpenCPN/plugins/… (the same)

This difference may create some issues initially "out of the box". Hopefully most plugins used standard environment variables or relative paths. Some plugins may have to be tweeked to improve the initial installation experience.

See https://github.com/OpenCPN/OpenCPN/issues/1635

